Project tree

Hi every body,

I want view the project tree, that means I want to view how module is linked to how module through which link module. Is it a simple wait to do that (even graphical format or textual format) ?

Thank You all for you help!
Babou - Thu Jul 29 09:47:10 EDT 2010

Re: Project tree
rmoskwa - Thu Jul 29 14:25:29 EDT 2010

Just curious, have you looked at the Analysis->Traceability Explorer menu selection for an open module?
A window will pop-up that has File and View menu items.
You have to configure you View.
You can only select in-link OR out-link paths.

Re: Project tree
Babou - Fri Jul 30 02:19:56 EDT 2010

Hi rmoskwa,

Thank you for you reply but the fonctionnality permits to explore links in a module. I want to see the tree of the modules in the project.
Something like :
Specification (module) <-- Validate (link module) -- Validation (module)
Specification (module) <-- Implement(link module) -- Design(module)
...

Re: Project tree
Mathias Mamsch - Sun Aug 01 07:58:28 EDT 2010

Babou - Fri Jul 30 02:19:56 EDT 2010
Hi rmoskwa,

Thank you for you reply but the fonctionnality permits to explore links in a module. I want to see the tree of the modules in the project.
Something like :
Specification (module) <-- Validate (link module) -- Validation (module)
Specification (module) <-- Implement(link module) -- Design(module)
...

Hi Babou, the easy way to go about this would be to just iterate the linksets in all link modules. The problem is, that you will not know if the linkset is actually used. Therefore you would need to have an additional script which will open the source module for a specific linkset and then count the links that are actually in there.

Wait, I have quite an old script, which will do that for you. Find it attached. Copy it to your lib/dxl/addins directory. It should be listed in the menu then. Launch it from any module in a project. It will go through all the modules in the project and list the links from and to that module. Then you can right-click in the list and choose "Export to Excel" and it will export the data to excel, where you can evaluate it.

Hope this helps, regards, Mathias

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
Attachments

attachment_14492664_LinkScan.zip

Re: Project tree
Babou - Mon Aug 02 02:13:42 EDT 2010

Hi Mathias

That seems answer to my problem. It's a good working basis.

Thank you very much

Re: Project tree
SystemAdmin - Mon Aug 16 13:22:50 EDT 2010

Babou - Mon Aug 02 02:13:42 EDT 2010
Hi Mathias

That seems answer to my problem. It's a good working basis.

Thank you very much

Hi,

One of the tools of the DOORS Rational RMF set (the "Explorer") is able to display the project structure and the traceability schema of your project and to support interaction.
It's better to use it on projects having a RMF model, but it can be used on any project.
here one screendump of this tool, in not RMF context (ie without any module type information)

But nothing perfect, it's a licensed tool !

Luc
Attachments

attachment_14510107_prj2.jpg

Re: Project tree
SystemAdmin - Mon Aug 16 18:14:54 EDT 2010

SystemAdmin - Mon Aug 16 13:22:50 EDT 2010
Hi,

One of the tools of the DOORS Rational RMF set (the "Explorer") is able to display the project structure and the traceability schema of your project and to support interaction.
It's better to use it on projects having a RMF model, but it can be used on any project.
here one screendump of this tool, in not RMF context (ie without any module type information)

But nothing perfect, it's a licensed tool !

Luc

Users have been asking for this type of graphical view of the relationships between modules in DOORS for years and years - in this day and age of visual interaction, having this kind of feature is expected as the norm - it shouldn't be a licensed feature, it should be a native built in feature like it is in many other IBM offerings.

BTW - is this graphical view interactive - for example - can I click on a graphical object to get more info, can graphical objects be moved around, can I edit module attribute values from here etc?

Paul Miller

Re: Project tree
SystemAdmin - Tue Aug 17 04:05:12 EDT 2010

SystemAdmin - Mon Aug 16 18:14:54 EDT 2010
Users have been asking for this type of graphical view of the relationships between modules in DOORS for years and years - in this day and age of visual interaction, having this kind of feature is expected as the norm - it shouldn't be a licensed feature, it should be a native built in feature like it is in many other IBM offerings.

BTW - is this graphical view interactive - for example - can I click on a graphical object to get more info, can graphical objects be moved around, can I edit module attribute values from here etc?

Paul Miller

Hi Paul,

Yes I am completely agree, it should have been in the core tool ... maybe in the future with the JAZZ evolution and some new capabilities in the tool!

The graphic view is interactive because you can click an item and apply operations on it: for example to create a new linkset between two modules to implement an association and set it as the default linkset. But you can't modify the layout of the drawing yourself, this is a choice. The tool implements a view concept wuith a lot of filtering options allowing to choose what information should be displayed and how, it it necessary to limit displayed graphic information on big projects. Each time you change an option, the layout may be different, and it will be complicated to make a new drawing yourself. For example you can decide to display the "satisfies" association or the "verifies" association, and the graph will be different. The layout of the graph is automatically computed by using the "Graphviz" package from ATT labs, with a COM (ole) integration between the DXL language and the Graphviz code (writen in C). Except tis, all the tool is developped in DXL. It supports three types of views:

model level (the conceptual data model of the project, created manually, in fact the RMF model of the project)
project level (modules and linksets, automatically extracted from the project)
object level (objects and links, automatically extracted from the project)

The object level should be seen as only a prototype and is not easy to use because too memory consuming.

Luc

Re: Project tree
Babou - Thu Oct 07 07:39:22 EDT 2010

I agree, this feature should be included as standard in Doors